Skip to content

docs(get-started): document Windows bootstrap script option - #3807

Merged
ericksoa merged 2 commits into
mainfrom
docs/windows-bootstrap-prep
May 19, 2026
Merged

docs(get-started): document Windows bootstrap script option#3807
ericksoa merged 2 commits into
mainfrom
docs/windows-bootstrap-prep

Conversation

@zyang-dev

@zyang-dev zyang-dev commented May 19, 2026

Copy link
Copy Markdown
Contributor

Summary

Documents the Windows bootstrap script as an optional preparation path before running the NemoClaw Quickstart. The update explains what the script configures, how reboot continuation works, and when users should continue inside Ubuntu.

Changes

  • Added a Windows bootstrap script option to the Windows preparation guide.
  • Documented the PowerShell invocation, Administrator/reboot behavior, Docker Desktop first-run handling, and advanced script parameters.
  • Updated the next-step guidance to distinguish bootstrap-script users from manual setup users.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Verification

  • npx prek run --all-files passes
  • npm test passes
  • Tests added or updated for new or changed behavior
  • No secrets, API keys, or credentials committed
  • Docs updated for user-facing behavior changes
  • make docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: zyang-dev 267119621+zyang-dev@users.noreply.github.com

Summary by CodeRabbit

  • Documentation
    • Added an “Option: Use the Bootstrap Script” to the Windows preparation guide, explaining how to run the provided bootstrap script to enable WSL2, prepare prerequisites, install/open Ubuntu, and set up Docker Desktop, including notes on execution policy, Administrator rights, reboot continuation, and verification. Updated “Next Step” guidance to follow the installer command printed by the script or proceed manually to the Quickstart.

Review Change Stack

Signed-off-by: zyang-dev <267119621+zyang-dev@users.noreply.github.com>
@coderabbitai

coderabbitai Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

Adds a Windows bootstrap-script option to the preparation guide and changes the "Next Step" instructions to branch between following the bootstrap-printed installer command or manually opening WSL and continuing to the Quickstart.

Changes

Windows Bootstrap Script Documentation

Layer / File(s) Summary
Bootstrap script option content
docs/get-started/windows-preparation.mdx, docs/get-started/windows-preparation.md
Adds an "Option: Use the Bootstrap Script" section with a PowerShell command to download/run the bootstrap script and explains the script's actions: enabling WSL features, installing/registering Ubuntu, installing/starting Docker Desktop, handling reboots/continuation, notes on permissions/execution policy, verification of Docker/WSL integration, and that NemoClaw installation still runs from the Ubuntu installer command.
Next Step branching guidance
docs/get-started/windows-preparation.mdx, docs/get-started/windows-preparation.md
Modifies "Next Step" to instruct bootstrap users to follow the Ubuntu installer command printed by the script, while directing manual-prep users to open WSL/Ubuntu and proceed with the Quickstart.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#3744: Implements the scripts/bootstrap-windows.ps1 script that this documentation guides users to execute.

Suggested labels

Platform: Windows/WSL

Suggested reviewers

  • ericksoa

Poem

🐰 I found a script on Windows land,
a PowerShell hop at my command.
WSL wakes, Docker hums along,
reboot, resume—then sing the song.
Now Ubuntu waits for the final hand.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically describes the main change: documenting a Windows bootstrap script option in the get-started guide.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch docs/windows-bootstrap-prep

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 ESLint

If the error stems from missing dependencies, add them to the package.json file. For unrecoverable errors (e.g., due to private dependencies), disable the tool in the CodeRabbit configuration.

ESLint skipped: no ESLint configuration detected in root package.json. To enable, add eslint to devDependencies.


Comment @coderabbitai help to get the list of available commands and usage tips.

@zyang-dev zyang-dev self-assigned this May 19, 2026
@github-actions

Copy link
Copy Markdown
Contributor

@github-actions

github-actions Bot commented May 19, 2026

Copy link
Copy Markdown
Contributor

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

  • None. Docs-only change. The PR updates Windows setup guidance text for the bootstrap script and next steps, but does not modify runtime code, scripts, workflows, policies, or tests that can affect user flows.

Optional E2E

  • None.

New E2E recommendations

  • None.

@ericksoa ericksoa left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved after adding the same Windows bootstrap guidance to the Fern-rendered MDX page.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (2)
docs/get-started/windows-preparation.mdx (2)

17-17: ⚡ Quick win

Use active voice.

"This guide has been tested" is passive. Rewrite in active voice, for example: "NVIDIA has tested this guide on x86-64" or "We have tested this guide on x86-64."

As per coding guidelines: "Active voice required. Flag passive constructions."

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/get-started/windows-preparation.mdx` at line 17, Change the passive
sentence "This guide has been tested on x86-64." to active voice; replace it
with a clear active phrasing such as "NVIDIA has tested this guide on x86-64."
or "We have tested this guide on x86-64." so the sentence uses an explicit
subject and active verb form.

39-41: ⚡ Quick win

Vary sentence structure to improve readability.

Three consecutive sentences begin with "If," which creates a repetitive rhythm. Consider combining or rephrasing one of these sentences to improve flow. For example, you could merge lines 39-40 or start line 41 differently: "Complete any first-run prompts from Docker Desktop and return to the PowerShell window."

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/get-started/windows-preparation.mdx` around lines 39 - 41, Three
consecutive sentences in the paragraph all start with "If," causing repetitive
rhythm; reword them to vary sentence structure by either merging the second and
third sentences into one conditional clause or by rephrasing the final sentence
to an imperative like "Complete any first-run prompts from Docker Desktop and
return to the PowerShell window." Locate the paragraph containing the three "If"
sentences and update it so one sentence begins differently (e.g., "Complete any
first-run prompts...") or combine the WSL reboot/register and Docker
reachability checks into a single flowing sentence to improve readability.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/get-started/windows-preparation.mdx`:
- Line 17: Change the passive sentence "This guide has been tested on x86-64."
to active voice; replace it with a clear active phrasing such as "NVIDIA has
tested this guide on x86-64." or "We have tested this guide on x86-64." so the
sentence uses an explicit subject and active verb form.
- Around line 39-41: Three consecutive sentences in the paragraph all start with
"If," causing repetitive rhythm; reword them to vary sentence structure by
either merging the second and third sentences into one conditional clause or by
rephrasing the final sentence to an imperative like "Complete any first-run
prompts from Docker Desktop and return to the PowerShell window." Locate the
paragraph containing the three "If" sentences and update it so one sentence
begins differently (e.g., "Complete any first-run prompts...") or combine the
WSL reboot/register and Docker reachability checks into a single flowing
sentence to improve readability.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0f39b98e-ad21-4c83-b134-0fc30917b912

📥 Commits

Reviewing files that changed from the base of the PR and between d0b5436 and e985edf.

📒 Files selected for processing (1)
  • docs/get-started/windows-preparation.mdx

@ericksoa
ericksoa merged commit 326f338 into main May 19, 2026
27 checks passed
@ericksoa
ericksoa deleted the docs/windows-bootstrap-prep branch May 19, 2026 20:14
@wscurran wscurran added platform: windows Affects native Windows environments platform: wsl Affects Windows Subsystem for Linux area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance and removed Platform: Windows/WSL labels Jun 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation, examples, guides, or docs build chore Build, CI, dependency, or tooling maintenance platform: windows Affects native Windows environments platform: wsl Affects Windows Subsystem for Linux

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants